Method and system for compressing structured descriptions of documents

ABSTRACT

An encoding method for enabling a decoder to decode a structured document having a structure defined in a first schema not accessible to the decoder and resulting from a change of a second schema accessible to the decoder, the first schema defining at least one information element which is derived from a corresponding element defined in the second schema, the encoding method comprising the steps of: encoding the document using said first and second schemas into a binary stream comprising for each elements of the document a binary sequence encoding the element, and inserting in the binary sequence encoding the derived element a reference designating the first schema in which the structure of the derived element is defined, said reference designating the first schema being defined in a schema reference list containing references to all schemas used for encoding the document, the schema reference list being made accessible to the decoder.

BACKGROUND OF THE INVENTION

[0001] 1. Field of the Invention

[0002] The invention relates in general to the field of computer systems, and more particularly to a method and system for the compression of structured documents using document descriptions that conforms to a generalized markup language, such as SGML (Standard Generalized Markup Language) and XML (Extensible Markup Language). Such documents may contain multimedia information.

[0003] 2. Description of the Related Art

[0004] In a few years, computer networks became the main media for communications. Computers can now be plugged to a shared network, operating systems allow applications to easily exchange messages, Internet infrastructure allows computers to find their interlocutor, applications use complex algorithms to synchronize themselves.

[0005] In such a context of interoperability, generalized markup languages provides solutions to deal with document processing. Indeed, the structure of a document plays a main role in the document usage. Formatting, printing or indexing a document is essentially made in accordance with its structure. SGML was initially made to easily dissociate document presentation and document structure and content. Because of its ability to encode structures, XML attracted attention from different communities interested in non-document applications. XML audience widened to include (among others) electronic commerce, databases and knowledge representation communities.

[0006] XML and more generally markup languages are now widely used to describe and structure documents (metadata). A structured document comprises several information elements which may be nested in each other. The information elements are identified and separated from each other by tags, which identify the element types of the information elements. A structured document generally comprises a first information element or base element which represents the entire document and which is identified by tags marking the start and end of the document. This first element comprises information sub-elements, for instance paragraphs of text, each information sub-element being identified by tags marking the start and end of the element. Tags may be associated with tag attributes that specifies one or more characteristics of the information element.

[0007] Tag content represents information that is generally intended to be displayed or manipulated by a user. Tag content may be optional or required according to the type of tag, and may contain other nested information sub-elements which in turn are delimited by tags and have content and attributes.

[0008] A structured document may be associated with a schema which reflects the rules that the structured document should verify in order to be considered as “valid”. It also contains information about default values, element and attributes types and type hierarchies. Validity ensures that a received document is conformant to the schema and thus has the intended meaning. Moreover it determines what is the nature, i.e. the type of each description item (information element or attributes). XML standard includes an XML Schema Language which is designed to specify a grammar for a class of XML documents having similar structures.

[0009] However XML is a verbose language and thus it is inefficient to be processed and costly to be transmitted. For this reason, ISO/IEC 15938-1 and more particularly MPEG-7 (Moving Picture Expert Group) proposes a method and a binary format for encoding (compressing) the description of a structured document and decoding such a binary format. This standard is more particularly designed to deal with highly structured data, such as multimedia data.

[0010] In order to gain compression efficiency, this method relies upon a schema analysis phase. During this phase, internal tables are computed to associate a binary code to each XML elements, types and attributes. This method mandates the full knowledge of the same schema by an encoder and a corresponding decoder.

[0011] When a schema used to encode structured documents requires to be extended, the best solution is to make the extended schema available to the decoder. However in specific cases, it is not possible to easily update the decoders in order to give them access to the extended schema.

SUMMARY OF THE INVENTION

[0012] An object of the invention is to provide a method for encoding a structured document in such a manner that the document can be partially decoded even if every needed schema are not known by the decoder.

[0013] Another object of the invention is to provide such an encoding method ensuring a backward and forward compatibility, i.e. enabling a decoder to at least partially decode a structured document having a structure defined in at least a first schema not accessible to the decoder and resulting from a change of at least a second schema accessible to the decoder, a structured document comprising information elements nested in each other, the information elements of the document being associated in at least a first and a second schemas with respective element types each defining the respective element structures of the information elements, the first schema being not accessible to a decoder and the second schema being accessible to the decoder, the first schema defining at least one derived information element which is derived from a corresponding element defined in the second schema.

[0014] According to the present invention, the encoding method comprises the steps of:

[0015] encoding the document using said first and second schemas into a binary stream comprising for each information elements of the document a binary sequence encoding the information element, and

[0016] inserting in the binary sequence encoding the derived information element a reference designating the first schema in which the structure of the derived element is defined, said reference designating the first schema being defined in a schema reference list containing references to all schemas used for encoding the document, the schema reference list being made accessible to the decoder.

[0017] According to an aspect of the present invention, the binary sequence encoding each element of the document comprises a content field containing an encoded value of the element and a length field placed before the content field and containing an encoded value of a length of the content field.

[0018] According to another aspect of the present invention, the derived information element is associated in the first schema to a structure type which is restricted with respect to the structure type of the corresponding information element in the second schema, the binary sequence encoding the derived element comprising a content field and appended to the content field, a reference to the first schema and a reference to the structure type of the derived element, defined in the second schema.

[0019] According to another aspect of the present invention, the derived information element is associated in the first schema to a structure type which is extended with respect to the structure type of the corresponding information element in the second schema, the structure type of the derived information element comprising a first part having the structure type of the corresponding information element defined in the second schema and a second part specific to the derived information element and having a structure type defined in the first schema, the binary sequence encoding the derived element comprising a content field comprising:

[0020] a field containing the reference to the second schema,

[0021] a field containing a structure type reference to the structure type of the corresponding element in the second schema,

[0022] a field containing an encoded value of the first part,

[0023] a field containing the reference to the first schema,

[0024] a field containing a structure type reference to the structure type of the second part, and

[0025] a field containing an encoded value of said second part.

[0026] According to another aspect of the present invention, the binary sequence encoding an information element comprises a substitution field including a substitution flag indicating whether or not the name of the information element is changed, and if the substitution flag indicates a change, an element name reference field containing a reference designating a new name of the information element, and a schema reference field containing a reference to a schema where the new name reference is defined.

[0027] According to another aspect of the present invention, the binary sequence encoding at least one information element in the encoded document comprises a schema status mode field having:

[0028] a first state indicating that the information element is not changed in the first schema with respect to a corresponding element in the second schema,

[0029] a second state indicating that none of sub-elements of the information element are changed in the first schema with respect to the corresponding element in the second schema, and

[0030] a third state indicating that the information element is changed in the first schema with respect to the corresponding element in the second schema,

[0031] the encoded information element comprising any schema reference and any other change information when the schema status mode field is in the first state, and none of sub-elements of the information element comprising a schema reference and any other change information when the schema status mode field is in the second state.

[0032] According to another aspect of the present invention, the binary sequence encoding at least one information element in the encoded document comprises a schema status mode field having a first state indicating that the information element is not changed in the first schema with respect to a corresponding element in the second schema, a second state indicating that none of sub-elements of the information element are changed in the first schema with respect to the corresponding element in the second schema, a third state indicating that the information element is changed in the first schema with respect to the corresponding element in the second schema, and a fourth state indicating that the information element is changed in the first schema with respect to the corresponding element in the second schema and that none of sub-elements of the information element are changed in the first schema with respect to the corresponding element in the second schema, the encoded information element comprising any schema reference and any other change information when the schema status mode field is in the first state, and none of sub-elements of the information element comprising a schema reference and any other change information when the schema status mode field is in the second state or fourth state.

[0033] According to another aspect of the present invention, the schema reference list comprising references to all schemas used for encoding the structured document is inserted in a header associated to the binary stream encoding the structured document.

[0034] Another object of the present invention is to provide a method for at least partially decode a binary stream encoding a structured document having a structure defined in at least a first schema not accessible to the decoder and resulting from a change of at least a second schema accessible to the decoder, a structured document comprising information elements nested in each other, the information elements of the document being associated in at least a first and a second schemas with respective element types each defining the respective element structures of the information elements, the first schema being not accessible to a decoder and the second schema being accessible to the decoder, the first schema defining at least one derived information element which is derived from a corresponding element defined in the second schema.

[0035] According to the present invention, the decoding method comprises the steps of:

[0036] sequentially reading and decoding a binary stream encoding the structured document using the second schema and detecting in the binary stream binary sequences encoding each information element of the document,

[0037] detecting in a binary sequence of an encoded element a reference to the first schema, as defined in a schema reference list known by the decoder,

[0038] identifying from the detection of said schema reference binary data relative to said first schema, and

[0039] skipping said binary data relative to said first schema during the sequential reading and decoding of said binary stream.

[0040] According to another aspect of the present invention, the binary sequence encoding each element of the document comprises a content field containing an encoded value of the element and a length field placed before the content field and containing the length encoded value, the length encoded value being used by the decoder for determining the end of the binary sequence encoding an element.

[0041] According to another aspect of the present invention, the decoding method further comprises the steps of:

[0042] reading and decoding a length coded value in the binary sequence containing a reference to the first schema, and

[0043] determining a length of binary data to skip as a function of the decoded length value and the position in the binary sequence of the reference to the first schema.

[0044] According to another aspect of the present invention, the derived information element is associated in the first schema to a structure type which is restricted with respect to the structure type of the corresponding information element in the second schema, the binary sequence encoding the derived element comprising a content field and appended to the content field, a reference to the first schema and a reference to the structure type of the derived element, defined in the second schema

[0045] According to another aspect of the present invention, the derived information element is associated in the first schema to a structure type which is extended with respect to the structure type of the corresponding information element in the second schema, the structure type of the derived information element comprising a first part having the structure type of the corresponding information element defined in the second schema and a second part specific to the derived information element and having a structure type defined in the first schema, the binary sequence encoding the derived element comprising a content field comprising:

[0046] a field containing the reference to the second schema,

[0047] a field containing a structure type reference to the structure type of the corresponding element in the second schema,

[0048] a field containing an encoded value of the first part,

[0049] a field containing the reference to the first schema,

[0050] a field containing a structure type reference to the structure type of the second part, and

[0051] a field containing an encoded value of said second part.

[0052] According to another aspect of the present invention, the derived information element has in the first schema a name which is changed with respect to the name of the corresponding information element in the second schema, the binary sequence encoding the derived element including a substitution field comprising a substitution flag indicated whether or not the name of the derived information element is changed, and if the substitution flag indicates a change, a schema reference field containing a reference to the first schema and an element name reference designating the name of the derived information element in the first schema.

[0053] According to another aspect of the present invention, the binary sequence encoding at least one information element in the encoded document comprises a schema status mode field having:

[0054] a first state indicating that the information element is not changed in the first schema with respect to a corresponding element in the second schema,

[0055] a second state indicating that none of sub-elements of the information element are changed in the first schema with respect to the corresponding element in the second schema, and

[0056] a third state indicating that the information element is changed in the first schema with respect to the corresponding element in the second schema,

[0057] the encoded information element comprising no schema reference and no other change information when the schema status mode field is in the first state, and none of sub-elements of the information element comprising a schema reference and any other change information when the schema status mode field is in the second state.

[0058] According to another aspect of the present invention, the binary sequence encoding at least one information element in the encoded document comprises a schema status mode field having a first state indicating that the information element is not changed in the first schema with respect to a corresponding element in the second schema, a second state indicating that none of sub-elements of the information element are changed in the first schema with respect to the corresponding element in the second schema, a third state indicating that the information element is changed in the first schema with respect to the corresponding element in the second schema, and a fourth state indicating that the information element is changed in the first schema with respect to the corresponding element in the second schema and that none of sub-elements of the information element are changed in the first schema with respect to the corresponding element in the second schema, the encoded information element comprising any schema reference and any other change information when the schema status mode field is in the first state, and none of sub-elements of the information element comprising a schema reference and any other change information when the schema status mode field is in the second state or fourth state.

[0059] According to another aspect of the present invention, the schema reference list comprising references to all schemas used for encoding the structured document is read in a header associated to the binary stream encoding the structured document.

BRIEF DESCRIPTION OF THE DRAWINGS

[0060] The various features of the present invention and its preferred embodiments may be better understood by referring to the following description and the accompanying drawings, wherein:

[0061]FIG. 1 depicts the binary format of a tree structure of a structured document according to MPEG-7 standard;

[0062]FIG. 2 depicts a block diagram of a MPEG-7 decoder;

[0063]FIG. 2a depicts a block diagram of a detailed part of the decoder represented in FIG. 2;

[0064]FIG. 3 depicts the binary format of an encoded information element according to the present invention;

[0065]FIG. 4 depicts element types defined with respect to each other in a tree structure;

[0066]FIG. 5 depicts a structured document comprising information elements organized in a tree structure.

DESCRIPTION OF PREFERRED EMBODIMENTS

[0067] Referring to FIG. 1, the binary format of an encoded structured document 1 according to MPEG-7 standard comprises a document header 2 which specifies encoding modes, and at least one structured information element or set of elements 3.

[0068] The document header 2 encodes the following parameters:

[0069] “allows_skipping”: this parameter specifies whether element lengths are coded in the encoded document; this parameter may have the following values:

[0070] 00—no length is coded,

[0071] 01—length is optionally coded,

[0072] 10—coding of length is mandatory.

[0073] “allows_partial_instantiation”: this parameter specifies whether or not all the sub-tree or structured information elements in the document are completely instantiated or not; this parameter may have the following values:

[0074] 0—no partial instantiation is allowed: all the elements of the document are present in the encoded document,

[0075] 1—partial instantiation is allowed.

[0076] “allows_subtyping”: this parameter specifies whether or not the sub-tree may contain polymorphisms, i.e. information elements or element attributes which may have different possible sub-types of a data type; this parameter may have the following values:

[0077] 0—no polymorphism is encoded in the sub-tree,

[0078] 1—polymorphism is allowed.

[0079] In FIG. 1, a set of structured information element 3 comprises an element set header 31 and elements 32 and/or sets of elements 3. The element set header 31 comprises:

[0080] a key which aims at clarifying any potential ambiguity about the type of the element during the decoding phase, and

[0081] a number Nb of occurrences of similar elements or element set of in the element 3 of the next higher hierarchical level.

[0082] If the schema defining the structure of the document specifies a single mandatory value for the type of an element or element set the number of occurrences is not present in the encoded document.

[0083] An element 32 comprises the following fields:

[0084] a length parameter 33 which specifies the length in bits of the encoded value of the element,

[0085] a type 35 containing a data type number specifying the structure of the element value and attributes of the element,

[0086] attribute values 36 of the element, these values being ordered for example in alphabetical order, and

[0087] a value 37 which encodes the value of the element itself; this field may contain one or more elements having a structure of the element 32 or element sets 3 or a simple value when the element has a simple type such as Integer, String, . . .

[0088] The length parameter 33 may be not present, depending on the value of the “allows_skipping” parameter in the header 2 of the encoded document. When the length is encoded in the element 32, a fast access to a particular element in the document is possible by skipping previous elements in the document using length information.

[0089] The fields 35, 36, 37 may be not present in the encoded element. If the possible data type of the element is unique in the schema of the document, the type number 35 is not encoded. The attribute values 36 are not encoded if the type specified in the schema does not have attributes. The value 37 of the element is not encoded if the element is empty for example in case of partial instantiation of the document.

[0090] Referring now to FIG. 2, a MPEG-7 decoder 10 comprises a schema compilator 11 designed to receive and process schemas 9 such as XML schemas, in order to obtain a binary syntax code 13 that is executed to decode encoded documents 7 that are applied in input of the decoder 10, the latter providing in output decoded documents 8 in format XML for example.

[0091] The compilation process of schemas relies on a prior schema analysis phase and aims at generating finite state automata 12 defined in the form of a binary syntax code. Each complex type defined in the processed schema is transformed into a finite state automaton expressing the complex type coding rules. The input encoded document 7 is applied to the decoder in the form of a binary stream on which the binary syntax code is executed.

[0092] In FIG. 2a, the schema compilation process 11 comprises a four phases. The first phase of schema realization consisting in flattening the type inheritances and in solving the Namespace support. This phase generates a realized schema 15. The second phase consists in generating a syntax tree from each complex type. The syntax trees 16 thus generated are then transformed in order to ease binary encoding and improve compression ratio. The third phase consists in normalizing the syntax trees generated by the previous phase in order to produce a signature for each tree node and then normalized syntax trees 17. These signatures are used in the following phase to generate a correspondence between the header keys appearing in the element headers 31 and a tree node. The fourth phase consists in generating the finite state automata 12 that are used in the decoding process.

[0093] In the schema realization phase, the schema is analyzed to list all the names used in the schema in order to attribute an expanded name to each element, attribute, type and group of elements, these names constituting the so called Namespace. The expanded names are constructed as a concatenation of a namespace identifier and an item name. Realized complex types are then generated by replacing the element references in each complex type by the definition of the elements referenced.

[0094] In the syntax tree generation phase, item nodes are generated by associating an element name to the type of the element. The item nodes linked by inclusion relations through group nodes constitute the syntax trees which are generated for each complex type. In specific cases, syntax trees are reduced to improve the compactness of the resulting binary format this process consisting in simplifying the complex type definitions in a non-destructive way.

[0095] Syntax tree normalization aims at giving unique name to every group node in the syntax tree. This process consists in ordering the nodes and finally gives a key to them, this key being needed during the automata construction phase.

[0096] A signature is generated for every element or group of elements. Every node signature is generated by the concatenation of its child node signatures. In case of an alternative group or a non-ordered group of nodes, the node signatures are alphabetically sorted and then appended. In case of a group of ordered nodes, the node signatures are appended in their order of definition in the schema. The item node signatures are equal to their element name.

[0097] In the finite state automata generation phase, a complex type automaton is recursively defined by the following rules:

[0098] 1. Every node of the syntax tree produces an automaton,

[0099] 2. A complex type automaton is the automaton produced by its root node,

[0100] 3. Every node automaton is generated by merging of its child automata, the nature of this merging being dependent of the nature of the node.

[0101] At the end of the process, automata are realized in order to produce their transitions coding key. These automata comprise two type states and an element transition linking the latter for each item node in the syntax trees. An element transition is crossed when the corresponding element appears in the input stream of the document to be decoded. A Type state triggers when activated a specific decoder which may be a specific data type decoder in the case of a simple type and a generic or a specific one in the case of a complex type.

[0102] In some cases, the schema defining the structure of a document requires to be extended or modified. If the new schema of the encoded document applied to the decoder is available, the latter can provide a full backward and forward compatibility, both for textual and binary format. Indeed, the entire description can be validated, namespaces can be attached to each element and attribute. Moreover, hierarchy of types is available and extensibility points can be made explicit for the application. Such a schema update solves many of the technical problems raised by extensibility and compatibility. However, the standard MPEG-7 does not presently provide any information about the schema to be used to decode an encoded document. Thus a decoder configured to use a schema cannot decode a document encoded with a modified schema (no forward compatibility). This problem can be solved merely by providing to the decoder an information about the schema to be used, prior to the decoding of the encoded document. Alternately, such automata or the syntax trees may be transformed into a binary syntax code which is executed by the decoder to decode a document in the form of an input binary stream.

[0103] In specific cases, the complexity induced by schema update might be problematic. Such a case occurs when it is not possible to easily update the decoders in order to give them access to a modified schema (forward compatibility), for example when the number of decoders to be updated is very high or when the decoders are not designed to use other schemas. In order to deal with these specific situations, the object of the present invention is to propose an information element binary format and an encoding and decoding method that allows a decoder to at least “partially” decode a document having a modified or extended structure with respect to a schema known by the decoder.

[0104] In this respect, at encoding phase a level of compatibility is chosen. This level is expressed in terms of a set of schemas for which compatibility should be ensured. The encoding process adds necessary redundancy to ensure the expected compatibility. In extreme case, if compatibility with only one current schema is needed, redundancy is removed, and the resulting binary encoded document is conformant to the current schema.

[0105] Basically the encoding process adds in the encoded document information about the schema used at encoding phase. This information comprises schema identifiers and length information to allow skipping of an element in the document encoded using a schema not available to the decoder.

[0106] The schema identifiers are defined by a schema identifier dictionary which is known from the decoder, for example inserted in the header 2 of the encoded document or inserted in a decoder initialization and configuration file used by the decoder. This schema identifier dictionary contains all possible schema identifiers that are to be used by the decoder to decode the encoded documents received. This dictionary can be read by the decoder using the following binary syntax: TABLE I SchemaDictionary(){ Number of bits NumberOfSchemaIdentifiers UINTVLC i = 0 while (i < NumberOfSchemaIdentifiers) { SchemaIdentifier [i] String i++ } }

[0107] where “NumberOfSchemaIdentifiers” and “SchemaIdentifier[ ]” represents respectively the number of schema identifiers in the dictionary and an array containing the schema identifiers, and “UINT_VLC” specifies a format to encode unsigned integers of indefinite size. In the format “UINT_VLC”, an integer is encoded by an infinite set of integer chunks, each chunk being composed of 5 bits. The first bit of each chunk specifies if an other chunk follows the current one, and the last 4 bits of the chunk encode the integer.

[0108] This binary syntax indicates that a schema dictionary comprises the number, followed by a list of schema identifiers in the form of character strings, the position of each schema identifier in the list automatically defining a schema number that may be used in the encoded document to identify a specific schema. The reading process of the dictionary comprises successively a step of reading in the dictionary the number of schemas “NumberOfSchemaIdentifiers”, a step of initializing a counter i, and loop instructions comprising a step of reading the i^(th) value in the “SchemaIdentifier[ ]” array, and a step of incrementing the counter i, with 0≦i<NumberOfSchemaIdentifiers. In the following table, the dictionary contains three schema identifiers, each schema being implicitly associated with a binary schema number defined by the rank of the schema identifier in the dictionary. TABLE 2 Schema Identifier Implicit Number S₁ 00 S₂ 01 S₃ 10

[0109] The length (number of bits) of a binary schema number is defined as a function of the number of schema identifiers in the dictionary and equal to E(log₂(NumberOfSchemaIdentifiers)), E(x) being equal to x rounded to the next higher integer.

[0110] As shown in FIG. 3, each type number field 35 in the encoded document is associated with a schema number field 38, the schema number corresponding to a schema identifier defined in the schema dictionary, this schema number identifying a schema in which the associated type is defined.

[0111] In this manner, an encoder and a decoder according to the present invention can use several schemas to encode and decode a document.

[0112] Three types of change are considered in XML language between an schema S0 and a modified schema S1, these change types being possibly combined together. A first type of change is the substitution of a global element name by another global element name, a global element being defined in a schema in an independent manner with respect to other elements (not nested in another element). Such a change is defined in XML schema language as follows.

[0113] In XML schema S0: . . . <complexType name=“S0:t0” base=“string”> . . . <element name=“e0” type=“S0:t0”/> . . .

[0114] and in XML schema S1: . . . <element name=“e1” type=“S0:t0” substitutionGroup=“S0:e0”/> . . .

[0115] This syntax defines a complex type “t0”, two elements named “e0” and “e1” having the type “t0”, the element “e1” being substituted to the element “e0”. Such an element “e1” having a value “value1” may appear in a XML document based on schema S1 as follows: . . . <e1>value1</e1> . . .

[0116] According to the invention, such a modification is encoded by adding in an element 32 substitution fields 4 comprising:

[0117] a substitution flag 41

[0118] a substituted element number 43, and

[0119] a schema number 42 where the element number 43 is defined.

[0120] When the substitution flag is set to 0, the following substitution fields 42 and 43 are not present in the encoded element.

[0121] The element “e1” encoded with schema S1 containing the definition of “e1” comprises as depicted in FIG. 3 the following field values:

[length]1[S 1][e 1][S 0][t 0][value1]

[0122] where:

[0123] [length] is the binary encoded length of the element, “1” is the value of the substitution flag indicating a substitution, [S1] and [S0] are the encoded numbers of schemas S1 and S0 as defined by the schema dictionary, [t0] is the encoded type number of type “t0”, [value1] is the encoded value of the value “value1” of element “e1” and [e1] is the encoded number of element “e1”. Such a binary code will be decoded according to the present invention by a decoder which only knows schema S0 (and therefore “e0”) and the decoded element can be interpreted as follows:

<e 0 DDL:IsSubstituted=“true”>value1</e 0>

[0124] Thus the decoder does not understand the meaning of [e1] and considers that “value1” is the value of element “e0” which is substituted by another unknown element.

[0125] A second type of change between a schema S0 and a new one S1 consists in deriving by restriction a new type t1 from a type “t0”. Such a restriction consists in reducing the number of maximal occurrences of at least one element or group of elements in the type definition, or increasing its number of minimal occurrences, or changing the type t0 to a sub-type t1, or defining a new group of elements that respect the constraints defined previously in the type t0.

[0126] Such changes are expressed in XML schema language in the following example. The XML schema S0 comprises the following text syntax: . . . <complexType name=“t0“> <sequence> <element name=“e1” type=“string” maxOccurs=“unbounded”/> </sequence> </complexType> . . . <element name=“e” type=“S0:t0”/> . . . In XML schema S1: . . . <complexType name=“t1”> <complexContent> <restriction base=“S0:t0”> <sequence> <element name=“e1” type=“string” maxOccurs=“1”/> </sequence> </restriction> </complexContent> </complexType> . . .

[0127] In this example, type “t0” is defined in XML schema language as comprising any number of occurrences of an element “e1”. Type “t1” is defined as a restriction of type “t0” and comprises 0 or one single element “e1” which is a particular case of type “t0”. Thus, type “t1]” enforces type “t0” constraints and the same binary format can be used.

[0128] The document to be encoded contains the following information: <S0:e xsi:type=“S1:t1”> <e1>value1</e1> </S0:e>

[0129] This means the document contains an element “e” having the type “t1” which is a sub-type of the expected type “t0” of element “e” defined in schema S0.

[0130] If forward compatibility is not required, this element can be encoded as follows:

[length]0[S 1][t 1][value1]

[0131] where “0” is the value of the substitution flag set to no substitution.

[0132] A decoder knowing schema S0 and not S1 decodes the fields [length] and [S1]. Since S1 is not defined in the schema dictionary, it deduces that the other fields relative to the element “e” cannot be interpreted using schema S0 and skips element “e” using the length information. If the decoder knows schema S1 (and therefore S0), it will retrieve the original structure of element “e”.

[0133] If forward compatibility is required, the element “e” is encoded according to the structure defined in FIG. 3 as follows:

[length]0[S 0][t 0][value1][S 1][t 1]

[0134] A decoder knowing both schemas S0 and S1 can decode all the fields of encoded element “e”. Then by comparing the length field and the length of the decoded stream, it deduces that there is no more sub-typing and will retrieve the original structure of element “e”. If the decoder knows schema S0 and not S1, it will decode the first part of the fields and skip [S1] and [t1] fields (using the length field). Thus it creates the following textual tree: <S0:e xsi:type=“S0:t0” DDL:isSubtype=“true”> <e1>value1</e1> </S0:e>

[0135] A third type of change between an old schema S0 and a new one S1 consists in deriving by extension a new type t1 from a type “t0”. If forward compatibility should be ensured, the new type t1 should be defined in two parts, the first part having the type “t0” and the second part having a the type “t1” which has to be defined in the new schema S1.

[0136] Such changes are expressed in XML schema language in the following example. The XML schema S0 comprises the following text: . . . <complexType name=“t0”> <sequence> <element name=“e1” type=“string”/> </sequence> </complexType> . . . <element name=“e” type=“S0:t0”/> . . .

[0137] In XML schema S1, the new type t1 is defined as an extension of the type t0 as follows: . . . <complexType name=“t1”> <complexContent> <extension base=“S0:t0”> <sequence> <element name=“e2” type=“string”/> </sequence> </extension> </complexContent> </complexType> . . .

[0138] If forward compatibility is required, the XML document to be encoded contains the following information: <S0:e xsi:type=“S1:t1”> <e1>value1</e1> <e2>value2</e2> </S0:e>

[0139] where value1 is the part of type “t0” in type “t1” and “value2” is the part specific to type “t1” and added to type “t0”. This information is encoded as follows:

[length]0[S 0][t 0][value1 ][S 1][t 1][value2]

[0140] If the decoder knows S0 (and not S1), it will decode the first part of the binary encoded information and skip t1 part (i.e. [t1][value2]) using the length information. Such a process leads to the following textual tree: <S0:e xsi:type=“S0:t0” ddl:isSubtype=“true”> <e1>value1</e1> </S0:e>

[0141] Thus the specific part of t1 will not be decoded. If the decoder knows both schemas S0 and S1, it will retrieve the original textual tree:

[0142] The above dispositions may be combined thus allowing the definition of complex hierarchies of types which may be defined in different schemas. FIG. 4 represents an example of such a hierarchy where types t5 and t6 are two extensions of a type t4 which is an extension of a type t3, type t3 being a restriction of a type t1. In a similar manner types t8 and t9 are respectively a restriction and an extension of a type t7 which is an extension of a type t2, type t2 being an extension of type t1. Considering that each of the types t1 through t9 are defined in respective different schemas S1 through S9, if compatibility is required with schemas S1, S3, S4 and S5, an element of type t5 is encoded in the following form:

[length]0[S 1][t 1][att1][value1][S 3][t 3][S 4][t 4][att4][value4][S 5][t 5][att5][value5]

[0143] where the fields [att-i] are the respective encoded attribute values of types t-i and [att-i][value-i] are the t-i part of type t5 (-i=1, 4 and 5). If compatibility is required with schemas S3 and S5, an element of type t5 is encoded in the following form:

[length]0[S 3][t 3][att3][value3][S 5][t 5][att5][value5]

[0144] where the fields [att3][value3] are the t1 part of type t5, coded according to type t3, and [att5][value5] are the t4+t5 part of type t5 coded according to t5.

[0145] Of course, the above mentioned first type of change between schemas may be combined with the second and third types of change by adding substitution fields 4 to the encoded elements.

[0146] In the foregoing description, forward compatibility is obtained by adding to the encoded document binary substitution fields (fields 41, 42, 43) and a schema number field in association to each element type. Therefore this solution increases the size of a resulting encoded document. In order to optimize encoding, it appears that parts of an encoded document are often linked to the same schema. In this respect, the present invention proposes to add in each encoded element 32 as illustrated on FIG. 3 a field 5 containing a schema status code representing a schema status mode. This field defines whether the corresponding element and sub-elements require specifications coming from a same schema or not. If the same schema is used for encoding (and decoding) an element and all sub-elements of the latter, the fields 38, 42 added for ensuring forward compatibility (containing schema numbers) are removed from the encoded element, thus increasing the resulting compression ratio.

[0147] The following table defines the possible values of the schema status code. TABLE 3 Schema Status Mode Value no change  0 freeze the schema 10 Change the schema 11

[0148] where:

[0149] “no change” means that the schema used for the decoding process of the element is the same than the one used for the element itself. Thus the element 32 does not contain a schema number field 38 and a substitution schema field 42.

[0150] “freeze the schema” means that the schema used for the decoding process of the element and all the sub-elements of the element (all the sub-tree of the element) is the same than the one used for the element itself. Thus the element 32 and all sub-elements of the element does not contain any schema number field 38, 42, and schema status field 5.

[0151] “change the schema” means that the schema of the element is changed. Thus the schema number fields 38, 42 are present in the element 32.

[0152] The mechanism controlled by the schema status code is illustrated by FIG. 5. This figure depicts the tree structure of a structured document comprising a main element 51 containing three sub-elements 52, 53, 54. The element 52 comprises two sub-elements 55, 56, and the element 54 three sub-elements 57, 58, 59. The element 55 comprises two sub-elements 60, 61.

[0153] The elements 51, 53, 54, 57 and 59 are encoded with a schema status code 5 set to 0 (“no change”). These elements do not contain any schema number fields 38, 42. The schema status code 5 of element 52 is set to 10 (“freeze the schema”). Thus all sub-elements 55, 56 and 60, 61 of element 52 are encoded with the same schema defined in the element 52, and these sub-elements do not contain any schema number fields 38, 42, and schema status code field 5.

[0154] The element 58 is modified and defined in another schema as comprising two sub-elements 62, 63. Thus the schema status code 5 of element 58 is set to 11 (“change the schema”). If the elements 62 and 63 are defined in the same schema as element 58, the schema status codes 5 of elements 62 and 63 are set to 0.

[0155] A further optimization may be performed by adding one possible value to the schema status code 5, as follows: TABLE 4 Schema Status Mode Value no change  0 freeze the schema  10 change the schema 110 Change and freeze the schema 111

[0156] When the schema status code of an element is set to 110 or 111, the schema of the element is changed. If this code is set to 110 the sub-elements of the latter contain a schema status mode field 5. When this code is set to 111, all the sub-elements of the element are encoded using the schema of the latter.

[0157] In the example of FIG. 5, the schema status code of element 58 may be set to 111 so as to specify that elements 62 and 63 are defined in the same schema as element 58. Thus no schema status code fields 5 are required in the elements 62 and 63. 

What is claimed is:
 1. An encoding method for enabling a decoder to at least partially decode a structured document having a structure defined in at least a first schema not accessible to the decoder and resulting from a change of at least a second schema accessible to the decoder, a structured document comprising information elements nested in each other, the information elements of the document being associated in at least a first and a second schemas with respective element types each defining the respective element structures of the information elements, the first schema being not accessible to a decoder and the second schema being accessible to the decoder, the first schema defining at least one derived information element which is derived from a corresponding element defined in the second schema, the encoding method comprising the steps of: encoding the document using said first and second schemas into a binary stream comprising for each information elements of the document a binary sequence encoding the information element, and inserting in the binary sequence encoding the derived information element a reference designating the first schema in which the structure of the derived element is defined, said reference designating the first schema being defined in a schema reference list containing references to all schemas used for encoding the document, the schema reference list being made accessible to the decoder.
 2. The encoding method according to claim 1, wherein the binary sequence encoding each element of the document comprises a content field containing an encoded value of the element and a length field placed before the content field and containing an encoded value of a length of the content field.
 3. The encoding method according to claim 2, wherein the derived information element is associated in the first schema to a structure type which is restricted with respect to the structure type of the corresponding information element in the second schema, the binary sequence encoding the derived element comprising a content field and appended to the content field, a reference to the first schema and a reference to the structure type of the derived element, defined in the second schema.
 4. The encoding method according to claim 2 or 3, wherein the derived information element is associated in the first schema to a structure type which is extended with respect to the structure type of the corresponding information element in the second schema, the structure type of the derived information element comprising a first part having the structure type of the corresponding information element defined in the second schema and a second part specific to the derived information element and having a structure type defined in the first schema, the binary sequence encoding the derived element comprising a content field comprising: a field containing the reference to the second schema, a field containing a structure type reference to the structure type of the corresponding element in the second schema, a field containing an encoded value of the first part, a field containing the reference to the first schema, a field containing a structure type reference to the structure type of the second part, and a field containing an encoded value of said second part.
 5. The encoding method according to anyone of claims 1 to 4, wherein the binary sequence encoding an information element comprises a substitution field including a substitution flag indicating whether or not the name of the information element is changed, and if the substitution flag indicates a change, an element name reference field containing a reference designating a new name of the information element, and a schema reference field containing a reference to a schema where the new name reference is defined.
 6. The encoding method according to anyone of claims 1 to 5, wherein the binary sequence encoding at least one information element in the encoded document comprises a schema status mode field having: a first state indicating that the information element is not changed in the first schema with respect to a corresponding element in the second schema, a second state indicating that none of sub-elements of the information element are changed in the first schema with respect to the corresponding element in the second schema, and a third state indicating that the information element is changed in the first schema with respect to the corresponding element in the second schema, the encoded information element comprising any schema reference and any other change information when the schema status mode field is in the first state, and none of sub-elements of the information element comprising a schema reference and any other change information when the schema status mode field is in the second state.
 7. The encoding method according to anyone of claims 1 to 5, wherein the binary sequence encoding at least one information element in the encoded document comprises a schema status mode field having a first state indicating that the information element is not changed in the first schema with respect to a corresponding element in the second schema, a second state indicating that none of sub-elements of the information element are changed in the first schema with respect to the corresponding element in the second schema, a third state indicating that the information element is changed in the first schema with respect to the corresponding element in the second schema, and a fourth state indicating that the information element is changed in the first schema with respect to the corresponding element in the second schema and that none of sub-elements of the information element are changed in the first schema with respect to the corresponding element in the second schema, the encoded information element comprising any schema reference and any other change information when the schema status mode field is in the first state, and none of sub-elements of the information element comprising a schema reference and any other change information when the schema status mode field is in the second state or fourth state.
 8. The encoding method according to anyone of claims 1 to 7, wherein the schema reference list comprising references to all schemas used for encoding the structured document is inserted in a header associated to the binary stream encoding the structured document.
 9. A decoding method for at least partially decode a binary stream encoding a structured document having a structure defined in at least a first schema not accessible to the decoder and resulting from a change of at least a second schema accessible to the decoder, a structured document comprising information elements nested in each other, the information elements of the document being associated in at least a first and a second schemas with respective element types each defining the respective element structures of the information elements, the first schema being not accessible to a decoder and the second schema being accessible to the decoder, the first schema defining at least one derived information element which is derived from a corresponding element defined in the second schema, the decoding method comprising the steps of: sequentially reading and decoding a binary stream encoding the structured document using the second schema and detecting in the binary stream binary sequences encoding each information element of the document, detecting in a binary sequence of an encoded element a reference to the first schema, as defined in a schema reference list known by the decoder, identifying from the detection of said schema reference binary data relative to said first schema, and skipping said binary data relative to said first schema during the sequential reading and decoding of said binary stream.
 10. The decoding method according to claim 9, wherein the binary sequence encoding each element of the document comprises a content field containing an encoded value of the element and a length field placed before the content field and containing the length encoded value, the length encoded value being used by the decoder for determining the end of the binary sequence encoding an element.
 11. The decoding method according to claim 10, further comprising the steps of: reading and decoding a length coded value in the binary sequence containing a reference to the first schema, and determining a length of binary data to skip as a function of the decoded length value and the position in the binary sequence of the reference to the first schema.
 12. The decoding method according to anyone of claims 9 to 11, wherein the derived information element is associated in the first schema to a structure type which is restricted with respect to the structure type of the corresponding information element in the second schema, the binary sequence encoding the derived element comprising a content field and appended to the content field, a reference to the first schema and a reference to the structure type of the derived element, defined in the second schema
 13. The decoding method according to anyone of claims 9 to 12, wherein the derived information element is associated in the first schema to a structure type which is extended with respect to the structure type of the corresponding information element in the second schema, the structure type of the derived information element comprising a first part having the structure type of the corresponding information element defined in the second schema and a second part specific to the derived information element and having a structure type defined in the first schema, the binary sequence encoding the derived element comprising a content field comprising: a field containing the reference to the second schema, a field containing a structure type reference to the structure type of the corresponding element in the second schema, a field containing an encoded value of the first part, a field containing the reference to the first schema, a field containing a structure type reference to the structure type of the second part, and a field containing an encoded value of said second part.
 14. The decoding method according to anyone of claims 9 to 13, wherein the derived information element has in the first schema a name which is changed with respect to the name of the corresponding information element in the second schema, the binary sequence encoding the derived element including a substitution field comprising a substitution flag indicated whether or not the name of the derived information element is changed, and if the substitution flag indicates a change, a schema reference field containing a reference to the first schema and an element name reference designating the name of the derived information element in the first schema.
 15. The decoding method according to anyone of claims 9 to 14, wherein the binary sequence encoding at least one information element in the encoded document comprises a schema status mode field having: a first state indicating that the information element is not changed in the first schema with respect to a corresponding element in the second schema, a second state indicating that none of sub-elements of the information element are changed in the first schema with respect to the corresponding element in the second schema, and a third state indicating that the information element is changed in the first schema with respect to the corresponding element in the second schema, the encoded information element comprising no schema reference and no other change information when the schema status mode field is in the first state, and none of sub-elements of the information element comprising a schema reference and any other change information when the schema status mode field is in the second state.
 16. The decoding method according to anyone of claims 9 to 14, wherein the binary sequence encoding at least one information element in the encoded document comprises a schema status mode field having a first state indicating that the information element is not changed in the first schema with respect to a corresponding element in the second schema, a second state indicating that none of sub-elements of the information element are changed in the first schema with respect to the corresponding element in the second schema, a third state indicating that the information element is changed in the first schema with respect to the corresponding element in the second schema, and a fourth state indicating that the information element is changed in the first schema with respect to the corresponding element in the second schema and that none of sub-elements of the information element are changed in the first schema with respect to the corresponding element in the second schema, the encoded information element comprising any schema reference and any other change information when the schema status mode field is in the first state, and none of sub-elements of the information element comprising a schema reference and any other change information when the schema status mode field is in the second state or fourth state.
 17. The decoding method according to anyone of claims 9 to 16, wherein the schema reference list comprising references to all schemas used for encoding the structured document is read in a header associated to the binary stream encoding the structured document. 